Digital Recording and Replay System for an Aircraft and Method for Reproduction of Onboard Instrumentation of an Aircraft

ABSTRACT

Digital recording and replay system ( 100 ) for an aircraft, comprising a Mission Computer (MC) with an Operational Flight Program (OFP) for generating instrument data (ID) for onboard instruments of the aircraft; a Mission Data Recorder (MDR) connected to said Mission Computer (MC) for recording said instrument data (ID); and a Mission Debriefing System (MDS); wherein the Mission Debriefing System (MDS) is configured to reproduce the onboard instruments of the aircraft based on instrument data (ID) retrieved from the Mission Data Recorder (MDR). Method for reproduction of onboard instrumentation of an aircraft, comprising the steps of connecting a Mission Data Recorder (MDR) to a Mission Computer (MC) of an aircraft having an Operational Flight Program (OFP) for generating instrument data (ID) for onboard instruments; recording instrument data (ID); providing a Mission Debrief System (MDS) and causing it to reproduce the onboard instruments of the aircraft based on instrument data (ID) retrieved from the Mission MDS Data Recorder (MDR).

PRIORITY

The present application claims priority from PCT/EP2009/066449 filedApr. 12, 2009.

FIELD OF THE INVENTION

The present invention relates to a Digital recording and replay systemfor an aircraft and to a method for reproduction of onboardinstrumentation of an aircraft.

BACKGROUND OF THE INVENTION

Quite often there is a need to be able to replay/reproduce the exactinstrumentation presented to the pilots of an aircraft after a flight.Furthermore, one needs to be able to present this instrumentation in thecontext of the particular scenario and also to be able to reconstructthe pilot's reaction to the events occurred during the flight. Inaddition the reaction of an airplane in response to the pilot's actionsneeds to be documented.

Several systems are known which are able to record aircraft parametersand store instrumentation data as a video and/or audio recording. Thesesystems are known as flight data recorders and cockpit voice/imagerecorders. They are usually placed in an aircraft for the purpose offacilitating the investigation of an aircraft accident or incident. Innewer aircrafts installation of cockpit image recorders has beenproposed to provide a video recording of the instruments within thecockpit. Such systems typically consist of a camera and microphonelocated in the cockpit to continuously record cockpit instrumentation,the outside viewing area, engine sounds, radio communications, andambient cockpit sounds. After an accident or incident, the flight datarecorders and cockpit voice/image recorders are retrieved and a videoand/or audio recording made during the flight is reconstructed alongwith recorded flight parameters.

However, known systems suffer from the major drawback that since theyrecord aircraft parameters and an audio and/or video feed they can'treliably reproduce the instruments exactly as shown to the pilot. Thisis due to the fact that the video images recorded might be blurred, thecamera view might be blocked, etc. or generally of low quality.Furthermore, due to the high storage capacity requirements for a videorecording covering all instruments, either the length of such arecording is limited, or some of the instruments are not covered by thevideo recording.

Furthermore, the reconstruction of the onboard instrumentation based ona video recording is a very time-consuming procedure prone to errors.

In an attempt to overcome these disadvantages, an other kind of knownsystem records merely aircraft parameters on the bases of which suchonboard instruments are constructed. These instruments are then to bereconstructed based on the recorded parameters. However, relying merelyon the set of recorded parameters does not necessarily allow a faithfulreconstruction of the onboard instrumentation. One cause for this is themalfunction of the avionics systems of the aircraft.

A special field where such a reconstruction of onboard reconstruction isfrequently performed is in the field of training aircrafts where theexact training environment is reconstructed for debrief and traininganalysis purposes. This field of application poses special requirementson such recording and replay systems, such as their ability to allow aquick and reliable reconstruction of the training environment includingonboard instrumentation but also of visual and audible alerts receivedthrough different channels of onboard avionics systems. Furthermore,such systems must be able to be reused numerous times and theirprocessing should be as straight-forward as possible.

Such training aircrafts are provided with a so-called mission computeras well with an operational flight program defining the trainingscenario performed by the pilot/trainee. Therefore, the recordedinstrument data needs to be recorded in relation with this scenariosince the onboard instruments are always in relation with theoperational flight program and only make sense in this context.

OBJECTIVE OF THE INVENTION

The objective of the present invention is thus to provide a recordingand replay system for an aircraft that is able to reliably reconstructthe onboard instruments of an aircraft, preferably a training aircraft,comprising a mission computer with an operational flight program. Afurther objective of the invention is to ensure that the onboardinstrumentation is easy to reconstruct and can store instrument datacovering a prolonged period of time.

Furthermore it is an objective of the present invention to provide amethod for reproduction of onboard instrumentation of an aircraft ableto reliably reconstruct the onboard instruments of an aircraft,preferably a training aircraft. Said method should allow quickreconstruction of onboard instruments of an aircraft brought in relationwith an operational flight program of a mission computer of theaircraft.

SUMMARY OF THE INVENTION

The above-identified objectives of the present invention are solved by arecording and replay system for an aircraft, comprising a missioncomputer with an operational flight program for generating instrumentdata for onboard instruments of the aircraft; a mission data recorderconnected to said mission computer for recording said instrument data asprocessed by mission computer with an operational flight program; and amission debriefing system; wherein the mission debriefing system isconfigured to reproduce the onboard instruments of the aircraft based oninstrument data retrieved from the mission data recorder.

The above-identified objectives of the present invention are also solvedby a method for reproduction of onboard instrumentation of an aircraft,comprising the steps of: connecting a mission data recorder to a missioncomputer of an aircraft having an operational flight program forgenerating instrument data for onboard instruments of the aircraft;recording instrument data as processed by mission computer with anoperational flight program and sent to the onboard instruments of theaircraft using said mission data recorder; providing a mission debriefsystem; and causing said mission debrief system to reproduce the onboardinstruments of the aircraft based on instrument data retrieved from themission data recorder.

The objectives identified above are solved by the present invention inthat instrument data for the onboard instruments of the aircraft, arerecorded by the mission data recorder instead of aircraft parameters orvideo recording of the actual instruments. In other words the systemrecords aircraft parameters where the signals have been processedthrough digital systems for accuracy and latency and relevance to theoperator of the aircraft. The instruments of the aircraft can then bereconstructed based on the recorded parameters. Relying on the set ofrecorded parameters gives a faithful reconstruction of the activitiesonboard instrumentation central to the operations of the aircraft,including an accurate representation of malfunctions. One cause for thisis the malfunction of the avionics systems of the aircraft which lies atthe heart of the computing systems used to process the data.

The concept of debrief reconstruction uses recorded parameters of theavionics systems to reconstruct the onboard instruments as thepilot/operator would see them during flight, without the use of videosystems.

This concept allows all pilot debrief to take place using thereconstructed instrumentation data, rather than basing debrief onrecorded video. The additional onboard instruments available due to therecording method are an additional training aid provided for very littleoverhead compared to recording the additional 20-30 video streams thatwould traditionally be required under such a debriefing system. Thedigital signal processing of incoming source signals such as barometricaltitude, airspeed or body lateral acceleration is carried out topresent the data to the operator, and this can be re-used by therecording system to maximize efficiency.

ADVANTAGEOUS EFFECTS

In view of the drawbacks of the prior art, the objective of the presentinvention and the inventive solution summarized above, the presentinvention has the main advantage that the data recorded reliablyreflects the onboard instrumentation as used by the operator, as opposedto known systems recording merely aircraft parameters that are supposedto result in some expected instrumentation display, while at the sametime simplifying the retrieval and minimizing the storage requirements,as compared to a recording of a video image of the instruments which issusceptible to errors in reconstruction, requires significantly morestorage capacity and might not even cover all onboard instruments.

BRIEF DESCRIPTION OF THE DRAWINGS

Further characteristics and advantages of the invention will in thefollowing be described in detail by means of the description and bymaking reference to the drawings. Which show:

FIG. 1 A schematic block diagram of the first embodiment of therecording and replay system according to the present invention;

FIG. 2A A schematic block diagram of the mission computer of an aircraftas being connected to a mission data recorder according to the presentinvention;

FIG. 2B A schematic block diagram depicting the integration of themission data recorder of the present invention with the avionics systemof an aircraft.

DESCRIPTION OF PREFERRED EMBODIMENTS

Certain terms will be used in this patent application, the formulationof which should not be interpreted to be limited by the specific termchosen, but as to relate to the general concept behind the specificterm.

In the context of the present application, training functionality shallmean the functionalities of a training aircraft which relate to thetraining of a pilot/trainee in an emulated environment within theaircraft. The training functionalities further relate to tacticalscenarios, simulated warfare, all these according to a trainingsyllabus.

The term aircraft shall mean in the context of the present applicationany kind of aircraft including recreational, civil but especiallytraining aircrafts providing tactical/training functionalities.

Hardware Architecture

FIG. 1 shows a schematic block diagram of the first embodiment of therecording and replay system according to the present invention. Thisfigure depicts the essential concept of the invention, i.e. theinteraction between the mission computer MC, the mission data recorderMDR and the mission debriefing system MDS.

The mission computer MC is a central part of the avionics system of atraining aircraft and comprises the operational flight program OFP, adataset defining the training scenario and/or mission of the aircraft,wherein the operational flight program OFP takes as input unprocesseddata, applies digital signal processing techniques for presentation tothe operator and generates instrument data ID for onboard instruments ofthe aircraft. The mission computer MC carries out digital signalprocessing of incoming source signals from a number of sources such asair data computers, radar altimeters and inertial reference systems thatsupply raw data transposed from the original analogue signalmeasurement. To ensure that the data is supplied to the pilot/operatorin a manner that is usable, the information is sampled and filtered toshow a relatively stable value whilst reflecting the current trends inthe aircraft parameters. Once this processing is carried out by theoperational flight program OFP within the mission computer MC, theprocessed instrument data ID can be presented to the operator, and thiscan be re-used by the mission data recorder MDR to maximize efficiencyin re-presenting this data in ground based debrief systems.

The mission data recorder MDR, a data recording and recovery device isconnected to the mission computer MC, is provided for recording theinstrument data ID generated by the operational flight program OFP. Therole of the mission data recorder MDR is to record instrument data ID toallow post flight mission analysis and debrief—to support the trainingof aircrew in the aircraft.

It shall be noted that the mission data recorder MDR is not areplacement or alternative for an accident or flight data recorder.

The mission debriefing system MDS is a data recovery and instrumentationreconstruction system, configured to reproduce the onboard instrumentsof the aircraft based on instrument data ID retrieved from the missiondata recorder MDR.

Mission Computer

FIG. 2A shows schematic block diagram of the mission computer MC of anaircraft as being connected to a mission data recorder MDR. Theconnection is preferably established via a mission bus 11. In apreferred embodiment of the present invention, the mission bus 11 isused to download new operational flight program OFP files into themission computer MC; download mission files; download digital map tiles;and to upload instrument data ID for recording by the mission datarecorder MDR. The mission computer MC initiates all transfers on themission bus 11. The mission computer MC mounts the removable memorymodule RMM of the mission data recorder MDR as a remote disk drive inorder to download mission files and/or to retrieve digital map tiles.Means for receiving said removable memory module RMM are provided withinthe mission data recorder MDR, such as a memory card slot or suitableconnectors.

The mission computer MC also controls the instrument data ID at theinstruments output for the onboard instruments such as theMulti-Function Display MFD and Up Front Control Panel UFCP for example.The mission computer MC has a graphics card dedicated to drawing theonboard instruments such as the displays for the multi-function displayMFD based on the instrument data ID.

The mission computer MC main board contains the operational flightprogram OFP that calculates the instrument data ID required for theonboard instruments. This instrument data ID is transferred to thegraphics cards.

To reduce loading, the packets of the instrument data ID are only sentwhen their data content has changed. Each packet is otherwise only sentevery few seconds to ensure subsequent playback synchronization isachieved rapidly during reconstruction.

The same instrument data ID can also be transferred to the mission datarecorder MDR due to the underlying similarity in the data structure.Therefore at the same time as sending the instrument data ID to thegraphics cards, the instrument data ID is sent to the mission datarecorder MDR preferably as UDP packets over the Ethernet link.

A header is added to the mission data recorder MDR output that definesthe instrument data ID contained within a packet. A small number ofadditional packets are included on the mission data recorder MDR outputthat use the same data architecture/structure but are not sent to thegraphics cards. These are included to aid reconstruction of othersystems other than the aircraft multi-function display MFD (e.g.Up-Front Control Panel UFCP or Primary Flight Display PFD).

Mission Data Recorder

FIG. 2B shows a schematic block diagram depicting the integration of themission data recorder MDR of the present invention with the avionicssystem of an aircraft.

The role of the mission data recorder MDR is to record instrument dataID to allow post flight mission analysis and debrief—to support thetraining of aircrew in the aircraft. In a preferred embodiment of thepresent invention, the mission data recorder MDR uses Ethernet input,video and audio inputs. The Ethernet input is from the mission computerMC, and carries the data used to generate the onboard instruments suchas the multi-function display MFD displays. The video shows head-updisplay HUD symbology overlaid on a forward view of the outside world.

The mission data recorder MDR is further connected to the audiomanagement unit AMU which controls all audio signals within theaircraft.

In a two-cockpit training aircraft, the head-up display HUD is installedin the front cockpit position, and incorporates a forward-lookingcamera. This camera produces a video image of the view ahead of theaircraft for display on the rear seat head-up display repeater HUDR. Thehead-up display HUD symbology is superimposed over the image of theoutside world on the head-up display repeater HUDR. In this case, thevideo is of the video seen on a head-up display repeater HUDR, and showshead-up display HUD symbology overlaid on a forward view of the outsideworld. In this two-cockpit training aircraft, the audio is of the frontcockpit headset audio so that all radio and intercom traffic and alerttones are available.

Additional event data, generated by the pilot via additional controls ofthe aircraft such as a console mounted event button or a stick mountedtrigger and pickle buttons, are also recorded by the mission datarecorder MDR

In a preferred embodiment, the mission computer MC transmits, via UDPbroadcast on the Ethernet ports 6003 (display data and instrumentation)and 6005 (Radar picture). This is the instrument data ID that is usedfor the generation of the onboard instruments such as multi-functiondisplay MFD display graphics. Some additional data that is available inthe mission computer MC and used on further onboard instruments such asthe primary flight display PFD is also transmitted on the Ethernet bus.

The mission data recorder MDR receives this UDP data, and records it.The mission data recorder MDR does not make any attempt to decode theUDP port 6003/6005 broadcast data. The resultant UDP contents arepreferably stored on a removable memory module RMM.

In a preferred implementation, the instrument data ID is stored on theremovable memory module RMM in files that are nominally 30 MB insize—this equates to approximately 5 to 6 minutes of recording time.Individual file sizes are limited so that if a file should becomecorrupted then only 5 to 6 minutes of data are lost.

Time stamp information is embedded within the recording, such that atreplay/reconstruction the actual time of the recording can bedetermined, for cross-relation to other external events and also toallow synchronized replay with the video and events data (and recordingsfrom other aircraft).

Preferably, the video and audio data are combined into a singlerecording stream. The audio is added to the video (left and rightchannels) to become a standard video with stereo audio channels. Theaudio/video is compressed for example using MPEG-2 compression, at 720by 480 pixels image size and 60 frames per second. The resultant MPEGdigital data is stored on the removable memory module RMM.

The data is recorded in files that are 30 seconds in length—these areapproximately 30 MB is size. The individual file sizes are limited sothat if a file should become corrupted then only 30 seconds of video arelost.

Time stamp information is embedded within the recording, such that atreplay the actual time of the recording can be determined, forcross-relation to other external events and also to allow synchronisedreplay with the head-down Ethernet recorded data and events data (andrecordings from other aircraft).

When the aircrew actuates an additional control of the aircraft such aspressing the event button, trigger or pickle button in either the frontor rear cockpits of a two-cockpit training aircraft, the missioncomputer MC detects this. The mission computer MC then passes a UDPpacket to the mission data recorder MDR with the event source code. Themission data recorder MDR records the time and event type.

In the replay/reconstruction, the event types and times can be listed.The time the event was made can be jumped to (offset by a definedamount, e.g., 5 seconds before the event was made) and the replay (videoand/or head-down) played from that point.

The removable memory module RMM operates as a conventional storage, withfiles stored within folders. Usually the removable memory module RMM isremoved/replaced for each flight.

In a preferred implementation there are 6 folders on the removablememory module RMM:

Channel1

Within Channel1 are sub-folders that are created at the start of eachrecording session (power-up). These sub-folders then hold the videorecording files for that recording session.

ENet

Within ENet are the Ethernet head-down recording files and log files forall the recording sessions.

Events

Within Events is a file for each recording session. Each file containsany event data recorded for that session.

Logs

Within Logs is a file for each recording session; each file contains loginformation for the video recording of that session.

Mission

The Mission folder is relevant to data upload.

MAP (may be renamed according to the ground planning and missioncomputer MC configurations).

The MAP folder is relevant to data upload.

Mission Debriefing System

The mission debriefing system MDS is designed to facilitate training byassisting the instructor to reinforce key learning points from thetraining sortie. It also provides a reliable indication of studentperformance on solo sorties.

In the preferred implementation, the mission debriefing system MDS readsthe Channel 1, ENet and Events folder of the removable memory module RMMto retrieve information as described above.

Means for receiving said removable memory module RMM are provided withinthe mission debriefing system MDS, such as a memory card slot orsuitable connectors.

The video information is replayed to give a combined head-up displayHUD/outside world picture. This information cannot be stored solely ininstrument data ID due to the inclusion of the outside world picturethat cannot faithfully be reproduced.

The mission debriefing system MDS displays/regenerates for example thefollowing onboard instruments based on instrument data ID:

Up-Front Control Panel (UFCP);

Left Multi Function Display (LMFD);

Primary Flight Display (PFD); and

Right Multi Function Display (RMFD).

Mission debriefing system MDS regenerates onboard instruments of theaircraft as per the instrument data ID recorded on the removable memorymodule RMM during the mission. The mission debriefing system MDS allowsthe user to regenerate any recorded multi-function display MFD page evenif it was not actually selected for display during the mission (i.e.selected by the pilot during flight) as all instrumentation is recordedregardless of display selected.

These additional displays are available at very little overhead comparedto recording the additional 20-30 video streams that would traditionallybe required under such a debriefing system.

The Events information is used to highlight within thereplay/reconstruction where certain events occurred. Events of interestto a debrief scenario may then be used to quickly navigate through themission.

In a further embodiment of the present invention, the mission debriefingsystem MDS is connectable to said mission data recorder MDR forretrieving said recorded instrument data ID and subsequently reproducethe onboard instruments of the aircraft based on instrument data IDretrieved from the mission data recorder MDR, said reproduction beingperformed within the aircraft using the onboard instruments of theaircraft. This has the advantage that since the reconstruction isperformed within the aircraft, the environment thus reconstructed willbe a true reconstruction of the environment during flight.

In an even further embodiment of the present invention, the missiondebriefing system MDS is connectable to a mission data recorder MDR forretrieving said recorded instrument data ID and subsequently reproducethe onboard instruments of the aircraft based on instrument data IDretrieved from the mission data recorder MDR, said reproduction beingperformed within a simulator comprising a mission computer MCcorresponding to said simulator replicating the onboard instruments ofthe aircraft. This has the advantage that since the reconstruction isperformed within a simulator replicating the aircraft, the environmentthus reconstructed will be a true reconstruction of the environmentduring flight without occupying an aircraft.

It will be understood that many variations could be adopted based on thespecific structure hereinbefore described without departing from thescope of the invention as defined in the following claims.

REFERENCE LIST

mission debriefing system MDS operational flight program OFP missiondata recorder MDR removable memory module RMM mission computer MC audiomanagement unit AMU instrument data ID multi-function display MFDprimary flight display PFD head-up display HUD head-up display repeaterHUDR recording and replay system 100 mission bus  11

1. A digital recording and replay system for an aircraft, comprising: aMission Computer with an Operational Flight Program configured todigital signal process input source signals and generate instrument dataof onboard instruments of an aircraft; a Mission Data Recorderoperatively connected to said Mission Computer configured to record saidinstrument data; and a Mission Debriefing System configured to reproducethe onboard instruments of the aircraft based on instrument dataretrieved from the Mission Data Recorder.
 2. A digital recording andreplay system for an aircraft according to claim 1, the Mission DataRecorder comprising a first means for receiving a Removable MemoryModule configured to store said instrument data.
 3. A digital recordingand replay system for an aircraft according to claim 2, the MissionDebriefing System comprising a second means for receiving a RemovableMemory Module configured to store said instrument data.
 4. A digitalrecording and replay system for an aircraft according to claim 1,wherein the Mission Debriefing System is operatively connectable to saidMission Data Recorder and configured to retrieve said recordedinstrument data and subsequently reproduce the onboard instruments ofthe aircraft within the aircraft using onboard instruments of theaircraft based on instrument data retrieved from the Mission DataRecorder.
 5. A digital recording and replay system for an aircraftaccording to claim 1, wherein said instrument data comprises parametersof an avionics system of the aircraft and wherein said reproduction bythe Mission Debriefing System comprises a reconstruction of a display asa pilot would see the display during a flight of the aircraft duringwhich said instrument data has been recorded.
 6. A digital recording andreplay system for an aircraft according to claim 1, wherein saidinstrument data comprises input data transferred to a graphics card ofthe aircraft and driving a display of the aircraft.
 7. A digitalrecording and replay system for an aircraft according to claim 6,wherein the Mission Computer is configured to send said input data aspackets to the Mission Data Recorder.
 8. A digital recording and replaysystem for an aircraft according to claim 7, wherein the MissionComputer is configured to include in said packets a header defining thedata contained within the packet.
 9. A digital recording and replaysystem for an aircraft according to claim 7, wherein the MissionComputer is configured to send additional packets to the Mission DataRecorder comprising data of additional aircraft avionics systems otherthan said display.
 10. A digital recording and replay system for anaircraft according to claim 1, wherein said instrument data comprisesevent data generated in response to pilot actions.
 11. A digitalrecording and replay system for an aircraft according to claim 10,wherein said event data is generated from onboard controls of theaircraft.
 12. A method of reproducing onboard instrumentation of anaircraft, comprising the steps of: operatively connecting a Mission DataRecorder to a Mission Computer of an aircraft having an OperationalFlight Program configured to generate instrument data of onboardinstruments of the aircraft; recording instrument data generated by theMission Computer using said Mission Data Recorder; and reproducing theonboard instruments of the aircraft with a Mission Debrief System basedon instrument data retrieved from the Mission Data Recorder.
 13. Amethod of reproducing onboard instrumentation of an aircraft accordingto claim 12, wherein the Mission Data Recorder comprises a first meansfor receiving a Removable Memory Module configured to store saidinstrument data, and further comprising the steps of inserting aRemovable Memory Module configured to store said instrument data intosaid first means, and storing said instrument data in the RemovableMemory Module.
 14. A method of reproducing onboard instrumentation of anaircraft according to claim 13, wherein the Mission Debriefing Systemcomprises a second means for receiving said Removable Memory Module, andfurther comprising the steps of: removing the Removable Memory Modulefrom said first means; and inserting the Removable Memory Module intothe second means.
 15. A method of reproducing onboard instrumentation ofan aircraft according to claim 12, wherein the reproducing step includesthe steps of: operatively connecting the Mission Debriefing System tothe Mission Data Recorder; retrieving said recorded instrument data; andreproducing the onboard instruments of the aircraft within the aircraftusing onboard instruments of the aircraft.
 16. A digital recording anddisplay system for an aircraft according to claim 3, further comprisinga Removable Memory Module configured to store said instrument data,removable from said first means, and insertable into the second means.